home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
AOL File Library: 4,101 to 4,200
/
aol-file-protocol-4400-4101-to-4200.zip
/
AOLDLs
/
Invoice & Inventory
/
ADIOS_ V8.02 Amway distributors
/
ADIOS8.exe
/
ADIOS.ERR
< prev
next >
Wrap
Text File
|
1993-03-10
|
4KB
|
99 lines
ERROR CODES
When running aDIOS make sure your AUTOEXEC.BAT or ADIOS.BAT have the
following statements included:
SET ADIOS=C:
DM001098 C:
If the colon is missing, you can get strange results when looking up
products. If you are running from a drive other than C use that drive name
followed by a colon. e.g. A:
Also, make sure your CONFIG.SYS includes:
1) a FILES=nn statement where nn is a number with a value of 20 or more.
2) a SHELL=X:\COMMAND.COM statement where X is the drive indicator where
COMMAND.COM can be found. If COMMAND.COM is in the same directory as the
ADIOS programs, this modification to CONFIG.SYS is not necessary.
---------------------------------------------------------------------------
Adios - run time error codes from Quick Basic.
When you get the error message to turn on the printer and call us with
the error code can be found on the list below. Many times you can fix the
problem without calling. TURBO errors are more technical and are listed
on the opposite side of this page.
5 Illegal function call - program was not started correctly
If the line number is 5564, see the comments about CONFIG.SYS above.
7 Out of memory
14 Out of string space
24 Device timeout
25 Device fault
27 Out of paper
51 Internal error
52 Bad filename or number
53 File not found
57 Device I-O error
61 Disk full
64 Bad file name
67 Too many files - check CONFIG.SYS FILES=20 or more
68 Device unavailable
70 Permission denied
71 Disk not ready
72 Disk-media error
75 Path File access error
76 Path not found
TURBO ERRORS
An error in an input or output operation at run-time results in in I/O er-
ror. If I/O checking is active (I compiler directive active), an I/O error
causes the program to halt and the following error message is displayed:
I/O error NN, PC-addr
Program aborted
Where NN is the I/O error number, and addr is the address in the program
code where the error occurred.
If I/O error checking is passive ({$I-}), an I/O error will not cause the
program to halt. Instead, all further I/O is suspended until the result of
the I/O operation has been examined with the standard function IOresult. If
I/O is attempted before IOresult is called after an error, a new error
occurs, possibly hanging the program.
The following contains explanations of all run-time error numbers. Notice
that the numbers are hexadecimal!
NOTE: The decimal equivalent has been added and is the first number to be
listed.
145 91 Seek beyond end-of-file.
153 99 Unexpected end-of-file.
1) Physical end-of-file encountered before EOF-character (Ctrl-Z)
when reading from a text file. 2) An attempt was made to read
beyond end-of-file on a defined file. 3) A Read or BlockRead is unable
to read the next sector of a defined file. Something may be wrong with
the file, or (in the case of BlockRead) you may be trying to read past
physical EOF.
240 F0 Disk write error.
Disk full while attempting to expand a file. This may occur with the
output operations Write, WriteLn, BlockWrite, and Flush, but also Read,
ReadLn, and Close may cause this error, as they cause the write buffer
to be flushed.
241 F1 Directory is full.
You are trying to Rewrite a flle, and there is no more room in the disk
directory.
243 F3 Too many files open.
Change CONFIG.SYS FILES= to a higher number.
255 FF File disappeared.
An attempt was made to Close a file which was no longer present in the disk
directory, e.g. because of an unexpected disk change.